Opening a game
When a user launches a provider's game, the user is redirected to the provider's OPEN_GAME_URL using the GET method. The game is usually opened in either an iframe or in a new tab.
This is a redirect-style launch. No JSON response is expected from the OPEN_GAME_URL. The provider should either serve the game directly at that URL or perform their own redirect to the actual game page.
Here is an example of a launch game request (GET):
https://provider-game-server.com/game-launch?token=0953560ec87a5a53918e9a457094a3f2&gameId=testgame&mode=0&language=en&platform=desktop¤cy=USD,
where https://provider-game-server.com/game-launch is the provider's OPEN_GAME_URL.
The following parameters are used:
| Parameter | Description | Mandatory | Type |
|---|---|---|---|
| token | A temporary token with a short lifespan (default: 60 seconds) used for requests to the system's login method. This parameter is not mandatory for demo mode. | - | string |
| gameId | Game ID | + | string |
| mode | Demo/real game (0 for real mode, 1 for fun mode) | + | integer |
| language | Session’s language parameter, written as two-letter codes based on the ISO 639-1 standard (e.g., en for English) | + | string |
| platform | Desktop, mobile | + | string |
| currency | Session’s currency (the parameter is not mandatory for demo mode) | - | string |
| casinoId | Casino operator ID (is sent at the provider's request) | - | string |
| lobbyUrl | Game lobby URL (is sent at the provider's request) | - | string |
It is also possible to send any additional parameters with fixed values required by the provider.